Scheduling and executing model components in response to un-modeled events detected during an execution of the model

ABSTRACT

A device may receive a model including a group of blocks, and may receive a command to execute the model. The device may assign a parameter sample time to a subset of blocks of the group of blocks. The parameter sample time may permit a block, of the subset of blocks, to be executed based on a parameter change event detected during the execution of the model. The device may cause the model to be executed after assigning the parameter sample time to the subset of blocks. The device may detect a parameter change event, associated with the model, prior to the execution of the model being completed. The parameter change event may include an event that is external to the execution of the model. The device may cause at least one block, of the subset of blocks, to be executed based on the detecting the parameter change event.

RELATED APPLICATION(S)

This application claims priority under 35 U.S.C. §119 to U.S.Provisional Patent Application No. 61/947,822, filed on Mar. 4, 2014,the content of which is incorporated by reference herein in itsentirety.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A-1C are diagrams of an overview of an example implementationdescribed herein;

FIG. 2 is a diagram of an example environment in which systems and/ormethods, described herein, may be implemented;

FIG. 3 is a diagram of example components of one or more devices of FIG.2;

FIGS. 4A-4I are diagrams of an example implementation of detecting anun-modeled event during an execution of a model, causing one or moreblocks, included in the model, to be re-executed in response to theun-modeled event, and continuing the execution of the model aftercausing the one or more blocks to be re-executed; and

FIGS. 5A and 5B are flow charts of an example process for detecting anun-modeled event during an execution of a model, causing one or moreblocks, included in the model, to be re-executed in response to theun-modeled event, and continuing the execution of the model aftercausing the one or more blocks to be re-executed.

DETAILED DESCRIPTION

The following detailed description of example implementations refers tothe accompanying drawings. The same reference numbers in differentdrawings may identify the same or similar elements.

A model (e.g., a graphical model), associated with a technical computingenvironment (TCE), may include a group of model components (e.g., agroup of blocks). The TCE may allow a block to be assigned to execute inresponse to an event that is described within the model (e.g., usingfunction call modeling semantics). However, the TCE may not allow theblock to be assigned to execute in response to an event that is notmodeled, such as a user interaction during model execution (e.g., amodification of a block parameter during model execution, an interactionwith a human machine interface (HMI) during model execution, etc.) oranother type of externally created event (e.g., an un-modeled event).While the processes and/or methods described herein are described interms of an externally created event in the form of a user modifying aparameter during model execution, these processes and/or methods mayequally apply to another type of externally created event.

With regard to modifying a parameter of a block during model execution,the TCE may require the user to choose between allowing modification(e.g., tuning) of the parameter and efficiently executing the model(e.g., since the block must be re-executed in order for the effect ofmodifying the parameter to be reflected in a result of executing themodel). The choice for scheduling execution of the block may be toeither execute the block once at the start of the execution of the modelor to execute the block repeatedly (e.g., periodically) during theexecution of the model. Implementations described herein provide a userwith both options by allowing the block to be executed as seldom aspossible while still allowing the impact of modifying the parameter tobe reflected in the result of executing the model. This may be achieved,for example, by implementing a parameter sample time in the TCE thatallows the block to be executed at startup (e.g., to initialize theblock) and allows the block to be re-executed when the parameter of theblock is modified to reflect parameter modification (e.g., to update astate of the block). Implementations described herein may allow fordetecting an un-modeled event during an execution of a model, causingone or more blocks, included in the model, to be re-executed in responseto the un-modeled event, and continuing the execution of the model aftercausing the one or more blocks to be re-executed. Causing the one ormore blocks of the model to be re-executed in response to the un-modeledevent, rather than being re-executed at each time step during modelexecution, may allow the performance of the model to be improved byincreasing efficiency of execution of the model without sacrificingaccuracy of a result determined based on executing the model.

FIGS. 1A-1C are diagrams of an overview of an example implementation 100described herein. For the purposes of example implementation 100, assumethat a TCE, hosted by a client device, has received (e.g., based oninput from a user) a model that includes a group of blocks, identifiedas block 1 through block 6.

As shown in FIG. 1A, and by reference number 105, the TCE may determinea sample time identifier associated with each block. For example, thesample time identifier may be determined based on user input, based ondefault configurations of each block, based on an analysis of the model,etc. As shown, the block 1 sample time identifier may identify acontinuous sample time for block 1 (e.g., indicating that block 1 is toproduce an output at each major and minor time step during execution ofthe model), the block 2 sample time identifier may identify a parametersample time for block 2 (e.g., indicating that block 2 is to produce anoutput once at the start of the execution of the model, and in responseto an externally created event that modifies a parameter of block 2),the block 3 sample time identifier may identify the parameter sampletime for block 3, the block 4 sample time identifier may identify aninherited sample time for block 4 (e.g., indicating that a sample timeis to be inherited from another block), the block 5 sample timeidentifier may identify the inherited sample time for block 5, and theblock 6 sample time identifier may identify the inherited sample timefor block 6. As shown by reference number 110, the user may indicate(e.g., by selecting an Execute menu item) that the TCE is to execute themodel.

As shown in FIG. 1B, and by reference number 115, the TCE may compilethe model and may assign sample times to each block (e.g., based on aninferencing mechanism such as sample time propagation rules associatedwith the TCE and/or based on the sample time identifiers associated witheach block). As shown, the TCE may assign the continuous sample time toblock 1, block 4, and block 6, and may assign the parameter sample timeto block 2, block 3, and block 5. As shown by reference number 120, theTCE may determine a set of blocks to which the parameter sample time hasbeen assigned (e.g., including block 2, block 3, and block 5) beforeproceeding with the execution of the model. As shown by reference number125, the TCE may begin the execution of the model by executing block 2,block 3, and block 5 one time (e.g., such that each block produces afirst output). As further shown, the TCE may then proceed withrepeatedly (e.g., at each time step) executing a set of blocks to whichthe continuous sample time has been assigned (e.g., block 1, block 4,and block 6). As shown, the TCE may continue to execute block 1, block4, and block 6 for a period of time (e.g., from time 0 to time X),without re-executing block 2, block 3, or block 5. As shown by referencenumber 130, the user may pause (e.g., by selecting a Pause menu item)the execution of the model at time X. While some implementations andexamples described herein may be described in the context of theparameter change event occurring and/or being detected causing anexecution of a model to be paused, in other implementations andexamples, the parameter change event may occur and/or be detectedwithout causing the execution of the model to be paused (e.g., such thatparameters may be modified without pausing the execution of the model).

As shown in FIG. 1C, and by reference number 135, the user may indicate(e.g., by selecting block 3) that the user wishes to modify a parameterof block 3, may modify (e.g., via a block 3 dialog box) the block 3parameter, and may finalize (e.g., by selecting an OK button themodification of the block 3 parameter. As shown, the TCE may determinethat an externally created event (e.g., a parameter change event) hasoccurred based on the user finalizing the block 3 parametermodification. As shown by reference number 140, the user may thenindicate (e.g., by selecting a Resume menu item) that the execution ofthe model is to resume.

As shown by reference number 145, the TCE may re-execute the set ofblocks to which the parameter sample time was assigned based ondetermining that the parameter change event occurred during theexecution of the model. In other words, the TCE may re-execute block 2,block 3, and block 5 one time (e.g., such that each block produces asecond output), and the TCE may once again proceed with repeatedlyexecuting block 1, block 4, and block 6. As shown, the TCE may continueto execute block 1, block 4, and block 6 from time X until the end ofthe model execution, without re-executing block 2, block 3, or block 5.As shown, the TCE may then provide a result of the execution of themodel. In this way, an un-modeled event may be detected during anexecution of a model, one or more blocks, included in the model, may bere-executed in response to the un-modeled event, and the execution ofthe model may continue after the one or more blocks are re-executed.

FIG. 2 is a diagram of an example environment 200 in which systemsand/or methods, described herein, may be implemented. As shown in FIG.2, environment 200 may include a client device 210, which may include atechnical computing environment (TCE) 220. Furthermore, environment 200may include a server device 230, which may include TCE 220, and anetwork 240. Devices of environment 200 may interconnect via wiredconnections, wireless connections, or a combination of wired andwireless connections.

Client device 210 may include one or more devices capable of receiving,generating, storing, processing, and/or providing information associatedwith executing a model in response to a parameter change event (e.g., anevent that is not modeled) associated with the model. For example,client device 210 may include a computing device, such as a desktopcomputer, a laptop computer, a tablet computer, a mobile phone (e.g., asmart phone, a radiotelephone, etc.), or a similar device. In someimplementations, client device 210 may be capable of receiving a model,compiling the model, assigning sample times to blocks included in themodel, causing the model to be executed, and/or providing a result ofexecuting the model. Additionally, or alternatively, client device 210may be capable of detecting a parameter change event, associated withthe model, and executing one or more blocks of the model based ondetecting the parameter change event. In some implementations, clientdevice 210 may receive information from and/or transmit information toserver device 230.

Client device 210 may host TCE 220. TCE 220 may include anyhardware-based logic or a combination of hardware and software-basedlogic that provides a computing environment that allows tasks to beperformed (e.g., by users) related to disciplines, such as, but notlimited to, mathematics, science, engineering, medicine, and business.TCE 220 may include a text-based environment (e.g., MATLAB® software), agraphically-based environment (e.g., Simulink® software, Stateflow®software, Simscape™ software, SimEvents® software, etc., by TheMathWorks, Inc.; VisSim by Visual Solutions; LabView® by NationalInstruments; StateWORKS Studio by StateWORKS, etc.), or another type ofenvironment, such as a hybrid environment that may include, for example,a text-based environment and a graphically-based environment.

TCE 220 may include a modeling system that may be used in the creationof a model and that may enable generation of executable code based onthe model. For example, TCE 220 may include a graphical modelingapplication that provides a user interface for a computing environment.Additionally, or alternatively, TCE 220 may include a graphical modelingapplication that provides a user interface for modeling and/orsimulating (e.g., by executing a model) a dynamic system (e.g., based ondifferential equations, difference equations, algebraic equations,discrete events, discrete states, stochastic relations, etc.). A dynamicsystem (either natural or man-made) may include a system, where aresponse of the system at any given time may be a function of inputstimuli associated with the system, a current state associated with thesystem, and/or a current time.

The system represented by a model may have various execution semanticsthat may be represented in the model as a collection of modelingentities, often referred to as blocks (e.g., including algorithmblocks). A block may generally refer to a portion of functionality thatmay be used in the model. The block may be represented graphically,textually, and/or stored in some form of internal representation. Also,a particular visual depiction used to represent the block, for examplein a graphical block diagram, may be a design choice. A block may behierarchical in that the block itself may comprise one or more blocksthat collectively make up the block.

A model may include blocks with relationships between the blocks, andthe relationships and/or the blocks may have attributes associated withthem. The blocks my include model elements, such as blocks and/or ports.The relationships may include model elements, such as lines (e.g.,connector lines) and references. The attributes may include modelelements, such as value information and meta information for the modelelement associated with the attributes. A model may be associated withconfiguration information. The configuration information may includeinformation for the model, such as model execution information (e.g.,numerical integration schemes, fundamental execution period, etc.),model diagnostic information (e.g., whether an algebraic loop should beconsidered an error or result in a warning), model optimizationinformation (e.g., whether model elements should share memory duringexecution), model processing information (e.g., whether commonfunctionality should be shared in code that is generated for a model),etc.

Additionally, or alternatively, a model may have executable semanticsand/or may be executable. An executable model may be a time based blockdiagram. A time based block diagram may consist, for example, of blocksconnected by lines (e.g., connector lines) that can represent signalvalues or that can represent an algorithm. The blocks may consist ofelemental dynamic systems such as a differential equation system (e.g.,to specify continuous-time behavior), a difference equation system(e.g., to specify discrete-time behavior), an algebraic equation system(e.g., to specify constraints), a state transition system (e.g., tospecify finite state machine behavior), an event based system (e.g., tospecify discrete event behavior), etc. The lines may represent signals(e.g., to specify input/output relations between blocks or to specifyexecution dependencies between blocks), variables (e.g., to specifyinformation shared between blocks), physical connections (e.g., tospecify electrical wires, pipes with volume flow, rigid mechanicalconnections, etc.), algorithms (e.g., to be applied to an input, anoutput, a value, etc.), or the like. The attributes may consist of metainformation such as sample times, dimensions, complexity (e.g., whetherthere is an imaginary component to a value), data type, etc. associatedwith the model elements.

In a time based block diagram, ports may be associated with blocks. Arelationship between two ports may be created by connecting a line(e.g., a connector line) between the two ports. Lines may also, oralternatively, be connected to other lines, for example by creatingbranch points. For instance, three or more ports can be connected byconnecting a line to each of the ports, and by connecting each of thelines to a common branch point for all of the lines. A common branchpoint for the lines that represent physical connections may be a dynamicor algebraic system (e.g., by buffering variable values, by summing allvariables of a certain type to 0, or by equating all variables of acertain type). A port may be an input port, an output port, an enableport, a trigger port, a function-call port, a publish port, a subscribeport, an exception port, an error port, a physics port, an entity flowport, a data flow port, a control flow port, etc.

Relationships between blocks may be causal and/or non-causal. Forexample, a model may include a block that represents a continuous-timeintegration block that may be causally related to a data logging blockby using a line (e.g., a connector line) to connect an output port ofthe continuous-time integration block to an input port of the datalogging block. Further, during execution of the model, the value storedby the continuous-time integrator may change as the current time of theexecution progresses. The value of the state of the continuous-timeintegrator may be available on the output port and the connection withthe input port of the data logging block may make this value availableto the data logging block.

In some implementations, a block may include or otherwise correspond toa non-causal modeling function or operation. An example of a non-causalmodeling function may include a function, operation, or equation thatmay be executed in different fashions depending on one or more inputs,circumstances, and/or conditions. Put another way, a non-causal modelingfunction or operation may include a function, operation, or equationthat does not have a predetermined causality. For instance, a non-causalmodeling function may include an equation (e.g., X=2Y) that can be usedto identify the value of one variable in the equation (e.g., “X”) uponreceiving an assigned value corresponding to the other variable (e.g.,“Y”). Similarly, if the value of the other variable (e.g., “Y”) wereprovided, the equation could also be used to determine the value of theone variable (e.g., “X”).

Server device 230 may include one or more devices capable of receiving,generating, storing, processing, and/or providing information associatedwith executing a model in response to a parameter change eventassociated with the model. For example, server device 230 may include acomputing device, such as a server, a desktop computer, a laptopcomputer, a tablet computer, or a similar device. In someimplementations, server device 230 may host TCE 220. In someimplementations, client device 210 may be used to access one or moreTCEs 220 running on one or more server devices 230. For example,multiple server devices 230 may be used to execute program code (e.g.,serially or in parallel), and may provide respective results ofexecuting the program code to client device 210.

In some implementations, client device 210 and server device 230 may beowned by different entities. For example, an end user may own clientdevice 210, and a third party may own server device 230. In someimplementations, server device 230 may include a device operating in acloud computing environment. In this way, front-end applications (e.g.,a user interface) may be separated from back-end applications (e.g.,program code execution).

Network 240 may include one or more wired and/or wireless networks. Forexample, network 240 may include a cellular network, a public landmobile network (PLMN), a local area network (LAN), a wide area network(WAN), a metropolitan area network (MAN), a telephone network (e.g., thePublic Switched Telephone Network (PSTN)), an ad hoc network, anintranet, the Internet, a fiber optic-based network, a private network,a cloud computing network, and/or a combination of these or other typesof networks.

The number and arrangement of devices and networks shown in FIG. 2 isprovided as an example. In practice, there may be additional devicesand/or networks, fewer devices and/or networks, different devices and/ornetworks, or differently arranged devices and/or networks than thoseshown in FIG. 2. Furthermore, two or more devices shown in FIG. 2 may beimplemented within a single device, or a single device shown in FIG. 2may be implemented as multiple, distributed devices. Additionally, oralternatively, a set of devices (e.g., one or more devices) ofenvironment 200 may perform one or more functions described as beingperformed by another set of devices of environment 200.

FIG. 3 is a diagram of example components of a device 300. Device 300may correspond to client device 210 and/or server device 230. In someimplementations, client device 210 and/or server device 230 may includeone or more devices 300 and/or one or more components of device 300. Asshown in FIG. 3, device 300 may include a bus 310, a processor 320, amemory 330, a storage component 340, an input component 350, an outputcomponent 360, and a communication interface 370.

Bus 310 may include a component that permits communication among thecomponents of device 300. Processor 320 may include a processor (e.g., acentral processing unit (CPU), a graphics processing unit (GPU), anaccelerated processing unit (APU), etc.), a microprocessor, and/or anyprocessing component (e.g., a field-programmable gate array (FPGA), anapplication-specific integrated circuit (ASIC), etc.) that interpretsand/or executes instructions, and/or that is designed to implement oneor more computing tasks. In some implementations, processor 320 mayinclude multiple processor cores for parallel computing. Memory 330 mayinclude a random access memory (RAM), a read only memory (ROM), and/oranother type of dynamic or static storage device (e.g., a flash memory,a magnetic memory, an optical memory, etc.) that stores informationand/or instructions for use by processor 320.

Storage component 340 may store information and/or software related tothe operation and use of device 300. For example, storage component 340may include a hard disk (e.g., a magnetic disk, an optical disk, amagneto-optic disk, a solid state disk, etc.), a compact disc (CD), adigital versatile disc (DVD), a floppy disk, a cartridge, a magnetictape, and/or another type of computer-readable medium, along with acorresponding drive. In some implementations, storage component 340 maystore TCE 220.

Input component 350 may include a component that permits device 300 toreceive information, such as via user input (e.g., a touch screendisplay, a keyboard, a keypad, a mouse, a button, a switch, amicrophone, etc.). Additionally, or alternatively, input component 350may include a sensor for sensing information (e.g., a global positioningsystem (GPS) component, an accelerometer, a gyroscope, an actuator,etc.). Output component 360 may include a component that provides outputinformation from device 300 (e.g., a display, a speaker, one or morelight-emitting diodes (LEDs), etc.).

Communication interface 370 may include a transceiver-like component(e.g., a transceiver, a separate receiver and transmitter, etc.) thatenables device 300 to communicate with other devices, such as via awired connection, a wireless connection, or a combination of wired andwireless connections. Communication interface 370 may permit device 300to receive information from another device and/or provide information toanother device. For example, communication interface 370 may include anEthernet interface, an optical interface, a coaxial interface, aninfrared interface, a radio frequency (RF) interface, a universal serialbus (USB) interface, a Wi-Fi interface, a cellular network interface, orthe like.

Device 300 may perform one or more processes described herein. Device300 may perform these processes in response to processor 320 executingsoftware instructions stored by a computer-readable medium, such asmemory 330 and/or storage component 340. A computer-readable medium isdefined herein as a non-transitory memory device. A memory deviceincludes memory space within a single physical storage device or memoryspace spread across multiple physical storage devices.

Software instructions may be read into memory 330 and/or storagecomponent 340 from another computer-readable medium or from anotherdevice via communication interface 370. When executed, softwareinstructions stored in memory 330 and/or storage component 340 may causeprocessor 320 to perform one or more processes described herein.Additionally, or alternatively, hardwired circuitry may be used in placeof or in combination with software instructions to perform one or moreprocesses described herein. Thus, implementations described herein arenot limited to any specific combination of hardware circuitry andsoftware.

The number and arrangement of components shown in FIG. 3 is provided asan example. In practice, device 300 may include additional components,fewer components, different components, or differently arrangedcomponents than those shown in FIG. 3. Additionally, or alternatively, aset of components (e.g., one or more components) of device 300 mayperform one or more functions described as being performed by anotherset of components of device 300.

FIGS. 4A-4I are diagrams of an example implementation 400 of detectingan un-modeled event during an execution of a model, causing one or moreblocks, included in the model, to be re-executed in response to theun-modeled event, and continuing the execution of the model aftercausing the one or more blocks to be re-executed. While the processesand/or methods described with regard to example implementation 400 aredescribed in terms of an un-modeled event in the form of a parameterchange event based on a user interaction, these processes and/or methodsmay equally apply to another type of un-modeled event, such as anun-modeled event associated with a programmatic instruction, aprogrammatic event, user initiated input, etc., received by TCE 220,that causes TCE 220 to modify, alter, update, etc. a parameter of one ormore blocks in response to the event. For the purposes of exampleimplementation 400, assume that TCE 220 allows for a parameter sampletime (e.g., a sample time indicating that a block is to produce anoutput once at the start of the execution of a model and in response toa externally created event that occurs during the model execution) to beassigned to one or more blocks included in a model, identified as ModelX.

As shown in FIG. 4A, and by reference number 405, Model X may include agroup of blocks including a sine block (e.g., Sine1), a first sum block(e.g., SumA), a first constant block (e.g., Constant1 with a constantvalue of 7), a second constant block (e.g., Constant2 with a constantvalue of 2), a lookup table block (e.g., Lookup1), a second sum block(e.g., SumB), an output block (e.g., Out1), and a scope block (e.g.,Scope1).

As shown by reference number 410, TCE 220 may determine a sample timeidentifier corresponding to each block of Model X. For example, thesample time identifier may be based on default block parameters, basedon user input, based on an analysis of Model X, etc. A sample timeidentifier, associated with a block, may include information thatidentifies a proposed sample time for the block. For the purposes ofexample implementation 400, assume that a sample time identifier of 0corresponds to a continuous sample time, that a sample time identifierof inf corresponds to the parameter sample time, and that a sample timeidentifier of −1 corresponds to an inherited sample time. As shown,Sine1 may be associated with the continuous sample time identifier(e.g., Sine1=0), SumA may be associated with the inherited sample timeidentifier (e.g., SumA=−1), Constant1 may be associated with theparameter sample time (e.g., Constant1=inf), SumB may be associated withthe inherited sample time identifier (e.g., SumB=−1), Constant2 may beassociated with the parameter sample time (e.g., Constant2=inf), Out1may be associated with the inherited sample time identifier (e.g.,Out1=−1), Lookup1 may be associated with the inherited sample timeidentifier (e.g., Lookup1=−1), and Scope1 may be associated with theinherited sample time identifier (e.g., Scope1=−1). As shown byreference number 415, TCE 220 may receive a command to execute Model X(e.g., based on the user selecting an Execute menu item associated withTCE 220). In some implementations, the information that identifiessample times for the blocks may include additional and/or differentinformation, such as a period (e.g., a time interval at which updatesoccur during simulation), an offset, (e.g., at interval indicating anupdate delay), or the like.

As shown in FIG. 4B, and by reference number 420, TCE 220 may compileModel X based on receiving the command to execute Model X. As shown, TCE220 may assign sample times to each of the blocks of Model X duringcompilation of the model. For example, sample times may be assignedbased on sample time propagation rules associated with TCE 220 and/orbased on rules associated with assigning each sample time. As shown, TCE220 may assign the continuous sample time to Sine1, SumA, and Out1. Asfurther shown, TCE 220 may assign a discrete sample time to Scope1(e.g., when Scope1 is configured such that Scope1 may inherit a discretesample time instead of a continuous sample time). As yet shown, TCE 220may assign the parameter sample time to Constant1, Constant2, Lookup1,and SumB. As shown by reference number 425, compiling the model mayfurther include identifying a set of parameter sample time blocksincluded in the model. As shown, TCE 220 may identify the group ofconnected blocks that includes Constant1, Constant2, Lookup1, and SumB.

As shown by reference number 430, compiling the model may furtherinclude generating execution lists associated with executing Model X. Anexecution list may include a list, a table etc. of blocks included inthe model that describes a schedule of the order of execution of theblocks. As shown, TCE 220 may generate a first execution list, ExecutionList 1, that includes the group of parameter sample time blocks, and maygenerate a second execution list, Execution list 2, that includes thegroup of blocks that was not assigned the parameter sample time.

As shown in FIG. 4C, and by reference number 435, TCE 220 may proceedwith executing Model X by executing the parameter sample time blocksincluded in Execution List 1 (e.g., Constant1, Constant2, Lookup1, andSumB) one time. As shown, Constant1 may output a value of 7 to Sum B. Asfurther shown, Constant2 may output a value of 2 to Lookup1, Lookup1 mayreceive the output value from Constant2, and may provide an output of 0to SumB. For example, the output value from Constant2 may be based onimplementing a lookup table included in Lookup1 and assuming that aninput value of 2 results in an output value of 0. As further shown, SumBmay receive the value of 7 from Constant1 and the value of 0 fromLookup1, and may provide an output of 7 to SumA. In the embodiment ofFIG. 4C, the parameter sample time blocks of Model X have only beenexecuted once by TCE 220.

As shown in FIG. 4D, and by reference number 440, TCE 220 may proceedwith executing the blocks included in Execution List 2 (e.g., Sine1,SumA, Out1, Scope1) after executing the group of parameter sample timeblocks. As shown, assume that the blocks included in Execution List 2are repeatedly executed as Model X is executed for twelve seconds (e.g.,from t=0 to t=12). For example, the blocks included in Execution List 2may be executed several times based on a sample time of Model X, such asa discrete sample time. For example, if the sample time of Model X is0.05 seconds, then the blocks of Execution List 2 would execute 24 timesif Model X is executed for 120 seconds before being paused. A user maypause execution of Model X when, as shown by reference number 445, theuser selects a Pause menu item.

As shown in FIG. 4E, and by reference number 450, the user may indicate(e.g., by double clicking Constant2) that the user wishes to modify aparameter of Constant2. As shown by reference number 455, TCE 220 maydisplay a dialog box, associated with Constant2, and the user may modifythe constant value parameter of Constant2 such that the new constantvalue of Constant2 is 4 (e.g., rather than 2). As shown by referencenumber 460, the user may indicate (e.g., by selecting and OK button)that the parameter is to be modified as indicated.

TCE 220 may detect, based on the parameter being modified, a parameterchange event. A parameter change event, associated with the model, mayinclude an externally created event that, when detected, may cause ablock (e.g., a parameter sample time block) to be re-executed. Anexternally created event may include an event that occurs outside of amodel. For example, a user may initiate an action (e.g., via an inputdevice of user device 210) via an input element (e.g., a button, a menuitem, etc.), associated with TCE 220, and the user initiated action maybe an externally created event that causes the block to be re-executed.As another example, a function, associated with TCE 220, may beconfigured to poll a memory location, and the polling of the memorylocation may be an externally created event that triggers (e.g., basedon detecting a particular value, a particular condition, etc. associatedwith the memory location) the block to be re-executed. As shown byreference number 465 and after detecting the parameter change eventassociated with Constant2, TCE 220 may receive user input (e.g., via aResume menu item) that the execution of Model X is to resume.

As shown in FIG. 4F, and by reference number 470, TCE 220 may determineExecution List 1 (e.g., that includes the parameter sample time blocks)based on receiving the indication to resume the execution of Model X,and as shown, may re-execute each of the parameter sample time blocksincluded in Execution List 1 (e.g., one time). Additionally, oralternatively, each of the parameter sample time blocks included inExecution List 1 may (e.g., automatically) re-execute (e.g., one time)when TCE 220 detects the parameter change event. As shown, Constant1,when re-executed, may output a value of 7 to Sum B. As further shown,Constant2 may output a value of 4 to Lookup 1, Lookup1 may receive theoutput value from Constant2, and may provide an output of −4 to SumB(e.g., based on implementing the lookup table included in Lookup1 andassuming that an input value of 4 results in an output value of −4). Asfurther shown, SumB may receive the value of 7 from Constant1 and thevalue of −4 from Lookup1, and may provide an output of 3 to SumA.

FIG. 4G illustrates an alternative to FIG. 4F. As shown in FIG. 4G, andby reference number 475, TCE 220 may determine Execution List 1 (e.g.,that includes the parameter sample time blocks) based on receiving theindication to resume the execution of Model X, and as shown, mayre-execute only those blocks that are affected by the parameter changeevent. Re-executing only those blocks that are affected by the parameterchange event may be referred to as adaptive re-execution. In otherwords, TCE 220 may not re-execute blocks unaffected by the parameterchange event (e.g., Constant1). As shown, Constant2, when re-executed,may output a value of 4 to Lookup 1, Lookup1 may receive the outputvalue from Constant2, and may provide an output of −4 to SumB (e.g.,based on implementing the lookup table included in Lookup1). As furthershown, SumB may determine (e.g., based on information stored by TCE 220)the value of 7 from Constant1 and may receive the value of −4 fromLookup1, and may provide an output of 3 to SumA. Notably, in thisalternative, TCE 220 applies adaptive re-execution by only executingparameter sample time blocks that are affected by the parameter changeevent (e.g., Constant2, Lookup1, and SumB) rather than all of theparameter sample time blocks.

As shown in FIG. 4H, and by reference number 480, TCE 220 may proceedwith executing the blocks included in Execution List 2 (e.g., Sine1,SumA, Out1, Scope1) after re-executing the group of parameter sampletime blocks. As shown, assume that the blocks included in Execution List2 are repeatedly executed as Model X is executed for anothertwenty-eight seconds (e.g., from t=12 to t=40). Assume that the modelexecution is complete after forty seconds, and that TCE 220 did notdetect another parameter change event during the final twenty-eightseconds during which Model X was executed.

As shown in FIG. 4I, and by reference number 485, TCE 220 may provide,via a user interface associated with Scope1, a result (e.g., a graph)associated with executing Model X. As indicated by reference number 490,the parameter sample time blocks of Model X may be executed only twiceduring the execution of Model X: one time during the initializationphase of the execution of Model X, and one time based on the parameterchange event detected by TCE 220 12 seconds after the execution of ModelX began. In this way (e.g., by implementing a parameter sample timewithin TCE 220), an un-modeled event (e.g., an externally created event)may be detected during an execution of a model, one or more blocks,included in the model, may be re-executed in response to the un-modeledevent, and the execution of the model may continue after the one or moreblocks are re-executed.

As indicated above, FIGS. 4A-4I are provided merely as an example. Otherexamples are possible and may differ from what was described with regardto FIGS. 4A-4I.

FIGS. 5A and 5B are flow charts of an example process 500 for detectingan un-modeled event during an execution of a model, causing one or moreblocks, included in the model, to be re-executed in response to theun-modeled event, and continuing the execution of the model aftercausing the one or more blocks to be re-executed. In someimplementations, one or more process blocks of FIG. 5 may be performedby client device 210. In some implementations, one or more processblocks of FIG. 5 may be performed by another device or a group ofdevices separate from or including client device 210, such as serverdevice 230. While the processes and/or methods described in process 500are described in terms of an externally created event in the form of auser modifying a parameter, associated with a block, during modelexecution, these processes and/or methods may equally apply to anothertype of externally created event.

As shown in FIG. 5A, process 500 may include receiving informationassociated with a set of blocks included in a model, the informationincluding a sample time identifier (block 505). For example, a user maycause client device 210 (e.g., TCE 220) to create or open a userinterface. The user interface (e.g., a model canvas) may not include anyblocks. The user may then add the set of blocks to the user interface.For example, in some implementations, client device 210 may receive acommand, from the user, that indicates that a block is to be added tothe user interface. Client device 210 may receive the command based, forexample, on detecting a selection of a particular menu item, entry of aparticular textual or audible input from the user, and/or entry of someother predetermined input that indicates a desire to add a block to theuser interface. As another example, client device 210 may receive input(e.g., a drag and drop) that indicates that a block, included in a blocklibrary associated with TCE 220, is to be added to the user interface.Based on the command, client device 210 may add the block to the userinterface. For example, client device 210 may add the block to a blockdiagram model represented via the user interface.

Additionally, or alternatively, client device 210 may receive a request,from a user of client device 210, to access the model that includes theset of blocks. The request may include information identifying themodel, such as a name of the model, and information identifying a memorylocation at which the model is stored. The memory location may belocated within client device 210 or external to, and possibly remotefrom, client device 210. Client device 210 may, based on receiving therequest, retrieve the model from the memory location. In someimplementations, client device 210 may provide, for display, a userinterface that depicts all or a portion of the set of blocks included inthe model.

In some implementations, client device 210 may determine a sample timeidentifier associated with each block of the set of blocks (e.g., asshown by reference numbers 405 and 410 of FIG. 4A). For example, clientdevice 210 may receive, from the user, input associated with a sampletime identifier corresponding to a block included in the model, andclient device 210 may determine the sample time identifier based on theuser input. As another example, client device 210 may determine thesample time identifier based on a default sample time identifierassociated with the block (e.g., when client device 210 storesinformation associated with the default sample time identifier). As yetanother example, client device 210 may determine the sample timeidentifier based on information stored by client device 210 (e.g., whenclient device 210 loads the model from memory and the model includesinformation associated with sample time identifiers of blocks includedin the model). As still another example, client device 210 may determinethe sample time identifier based on retrieving the sample timeidentifier from a remote source, such as server device 230. As a finalexample, client device 210 may determine the sample time identifierbased on analyzing the model and specifying a sample time identifier forthe block. In this example, client device 210 may permit the user tomodify the sample time identifier.

A sample time identifier, associated with a block, may includeinformation that identifies a proposed sample time for the block. Thesample time identifier may identify a proposed sample time since theblock may be assigned a different sample time during sample timeassignment, as discussed below. For example, the sample time identifiermay include information that identifies a continuous sample time (e.g.,indicating that the block is to produce an output at each major and/orminor time step during execution of the model), a discrete sample time(e.g., indicating that the block is to produce an output at particularintervals of time during model execution), a constant sample time (e.g.,indicating that the block is to produce an output one time at the startof the model execution), a parameter sample time (e.g., indicating thatthe block is to produce an output once at the start of the execution ofthe model and in response to an externally created event that occursduring the model execution), an inherited sample time (e.g., indicatingthat the sample time of the block is to be inherited from another blockincluded in the model), and/or another type of sample time.

As further shown in FIG. 5A, process 500 may include receiving a commandto execute the model (block 510). For example, client device 210 (e.g.,TCE 220) may receive a command, from the user, to execute the modelincluding the set of blocks. In some implementations, client device 210may receive the command based on detecting a selection of a particularmenu item (e.g., as shown by reference number 415 of FIG. 4A), entry ofa particular textual or audible input from the user, and/or entry ofsome other predetermined input that identifies the desire to analyze orexecute the model.

As further shown in FIG. 5A, process 500 may include compiling the modelbased on receiving the command to execute the model (block 515). Forexample, client device 210 (e.g., TCE 220) may compile the model basedon receiving the command to execute the model (e.g., as shown byreference number 420 of FIG. 4B). In some implementations, compiling themodel may include determining a manner in which the set of blocks,included in the model, are connected (e.g., which outputs are connectedto which inputs), determining characteristics associated withconnections and/or blocks included in the model (e.g., a data type, adimensionality, a complexity, etc.), assigning memory locations toparticular blocks and/or connections, and/or designating an order inwhich the set of blocks are going to be executed (e.g., scheduling themodel based on semantic rules, such as a synchronous data flow rule, adynamic data flow rule, a Boolean data flow rule, a Kahn process networkrule, a Petri net rule, a discrete event system rule, etc.).Additionally, or alternatively, compiling the model may includegenerating one or more execution lists associated with the model,determining computations that are actually going to be executed,determining a buffer allocation and/or allocating buffer spaceassociated with model execution (e.g., determining and/or allocating anumber and/or size of data buffers for the blocks and/or connections),determining time delays associated with the set of blocks, determiningmemory consumption and/or memory accesses associated with the set ofblocks, and/or determining other information relating to size,performance, or ordering of the set of blocks included in the model.

In some implementations, compiling the model may include assigning asample time to at least one block (e.g., each block) included in themodel. For example, client device 210 may assign a sample time to eachblock of the set of blocks included in the model. In someimplementations, client device 210 may assign the sample times based onsample time propagation rules associated with TCE 220. For example,client device 210 may implement a set of propagation rules associatedwith TCE 220 in order to assign a sample time to each block included inthe model. In some implementations, a block may be assigned a sampletime that corresponds to the sample time identifier associated with theblock. Alternatively, the block may be assigned a sample time differentthan the sample time that corresponds to the sample time identifier(e.g., when the propagation rules cause the different sample time to beassigned to the block).

As discussed above, client device 210 may assign the parameter sampletime to one or more of the blocks included in the model. In someimplementations, a set of parameter sample time rules, stored by clientdevice 210, may govern whether a block may be assigned the parametersample time. For example, a first parameter sample time rule mayindicate that the block is to be assigned the parameter sample time ifthe block would be assigned a constant sample time (e.g., when the useof the parameter sample time is implemented to replace the use of theconstant sample time). Similarly, a second parameter sample time rulemay indicate that the block is to be assigned the parameter sample timewhen the block would have been assigned the constant sample but for theblock (or another block that dictates the sample time of the block)being configured to allow for tunable parameters. A third parametersample time rule may indicate that the block may not be assigned theparameter sample time if the block drives a subsystem control port(e.g., an enabled subsystem, a triggered subsystem, etc.). A fourthparameter sample time rule may indicate that the block may not beassigned the parameter sample time if the block includes an updatemethod. Alternatively, the block may be assigned the parameter sampletime if the block includes an update method, but may indicate that theupdate method of the block may not be executed during model execution. Afifth parameter sample time rule may indicate that the block may beassigned the parameter sample time even if the block is included in aconditionally executed subsystem (e.g., conditionally executed subsystemboundaries may be ignored). Additionally, or alternatively, the blockmay be assigned the parameter sample time based on another rule.

In some implementations, client device 210 may assign sample times toeach of the blocks included in the model, and client device 210 mayupdate a display, associated with the model, based on the assignedsample times. For example, client device 210 may assign the sample timesto each of the blocks included in the model, and client device 210 mayupdate a display, associated with model, based on a color scheme thatcorresponds to the assigned sample times (e.g., when blocks assigned theparameter sample time may be displayed in a particular colorcorresponding to the parameter sample time). In some implementations,client device 210 may update the display to indicate the sample timesusing a form of visualization of than a color scheme, such as agrayscale scheme, a labeling scheme, a hatching scheme, or the like.

Additionally, or alternatively, compiling the model may includeassigning blocks to computational resources for execution and/or settinga rate at which blocks in the model are to execute. Additionally, oralternatively, compiling the model may include determining staticscheduling information associated with the model. For example, clientdevice 210 may analyze the model (e.g., based on rate monotonicscheduling (RMS), based on output dependencies associated with themodel) in order to determine static scheduling information associatedwith the model. In some implementations, the static schedulinginformation may be used, during execution of the model, in order todetermine an order associated with re-executing the one or moreparameter sample time blocks. Additionally, or alternatively, compilingthe model may include generating program code for executing the model.The program code may include program code describing the set of blocksincluded in the model. Additionally, or alternatively, the program codemay include instructions for multi-rate execution (e.g., with differentblocks being executed at different rates) and/or multi-task execution(e.g., with different blocks being executed using differentcomputational resources) of the model. In some implementations, clientdevice 210 may store the program code for later execution.

In some implementations, for program code generated from the model,different workflows and target environments may have differentrequirements for the parameter sample time. As one example, if thetarget environment (e.g., a simulation target such as the SimulinkAccelerator) supports a new model level entry point for the parametersample time, then such an entry point may be generated and TCE 220 maycall the entry point appropriately in response to an externally createdevent. In this context, appropriately may be defined as scheduling thecall inside the execution context of downstream blocks that use a resultas input (e.g., in order to avoid data corruption). This may requiremultiple entry points to be created when there are multiple consumerthreads.

An alternative for the generated code may be to generate the separateentry point function for blocks with the parameter sample time even ifthe target environment does not support a new model level entry pointfor the parameter sample time, and (a) ensure that the entry point iscalled by calling the entry point from a method to compute output valuesof model blocks (e.g., an output method) for the base rate of the modelwith an appropriate guard, and (b) adding rate transition protectioncode to guard data passing between outputs of the blocks with theparameter sample time and input of blocks with other sample times.

As another example, if the workflow is primarily concerned with aperformance metric, such as CPU throughput, and does not need to tuneparameters of the model after the model begins to be executed, then theprogram code for blocks with the parameter sample time may be generatedinto the start method of the model. Similarly, the program code forblocks with the parameter sample time may be generated into the startmethod when a parameter referenced by the parameter sample time blocksis not to be modified during the execution of the model (e.g., when theparameter is defined as being non-tunable after the execution of themodel has begun, as described below). In some implementations, TCE 220may determine (e.g., based on user input) that all parameters referencedby one or more of the parameter sample time blocks are not to bemodified during the execution of the model (e.g., on a global basis).Additionally, or alternatively, TCE 220 may determine that one or moreparticular parameters, referenced by one or more of the parameter sampletime blocks, are not to be modified during the execution of the model(e.g., on a local basis).

As yet another example, the program code for blocks with the parametersample time may be generated into an output method at the rate of blocksthat are downstream from the blocks with the parameter sample time. Inthis situation, care may be needed to ensure that the parameter valuechanges caused by the externally created event happen synchronously withthe execution of the program code that reads the values (e.g., in orderto prevent data corruption).

In some implementations, the manner in which the program code for theparameter sample time blocks is generated may be based on a performancemetric prioritization associated with generating the program code. Forexample, the user may indicate (e.g., via a code generation optimizationtool associated with TCE 220), that minimizing RAM usage is a higherpriority than maximizing CPU throughput when executing program codegenerated based on the model. In this example, TCE 220 may determinethat the program code for the parameter sample time blocks is to begenerated into the output method of blocks that are downstream from theparameter sample time blocks (e.g., to decrease RAM usage duringexecution of the program code). As another example, the user mayindicate that maximizing CPU throughput is a higher priority thanminimizing RAM usage when executing code generated based on the model.In this example, TCE 220 may determine that the program code for theparameter sample time blocks is to be generated into the start method ofthe model (e.g., to increase CPU throughput).

Additionally, or alternatively, the program code for the parametersample time blocks may be generated based on applying constant foldingto two or more connected parameter sample time blocks. For example,assume that, during code generation, TCE 220 determines, based onparameter definitions corresponding to one or more parameters referencedby two or more connected parameter sample time blocks, that the one ormore parameters are not tunable (e.g., that the one or more parametersmay not be modified). In this example, TCE 220 may compute an output ofthe two or more connected parameter sample time blocks during codegeneration associated with the two or more connected blocks, and maystore the output (e.g., in a data structure associated with constantblock outputs for the model) such that the output may be referenced inprogram code generated for the model. In this way, the program code forthe model may be generated such that the output of the two or moreconnected parameter sample time blocks may be statically represented inthe program code (e.g., such that no program code needs to be executedin order to determine the output of the two or more connected parametersample time blocks).

Additionally, or alternatively, compiling the model may includeidentifying a block, of the set of blocks, to which that parametersample time has been assigned (herein referred to as a parameter sampletime block), and/or may include generating an execution list thatincludes the block, as discussed below with regard to blocks 520 and525, respectively.

As further shown in FIG. 5A, process 500 may include identifying ablock, of the set of blocks, to which a parameter sample time isassigned (block 520). For example, client device 210 (e.g., TCE 220) mayidentify a block, of the set of blocks, to which the parameter sampletime is assigned. In some implementations, client device 210 mayidentify the parameter sample time block when client device 210 compilesthe model. Additionally, or alternatively, client device 210 mayidentify the parameter sample time block when client device 210 assignssample times to each block of the set of blocks.

In some implementations, client device 210 may identify the parametersample time block based on assigning the parameter sample time to theblock in the manner discussed above. In some implementations, clientdevice 210 may identify multiple parameter sample time blocks.Additionally, or alternatively, client device 210 may identify a groupof connected parameter sample time blocks, an example of which isdescribed above with reference number 425 in FIG. 4B. Additionally, oralternatively, client device 210 may identify multiple groups ofconnected parameter sample time blocks (e.g., a first group of connectedparameter sample time blocks and a second group of connected parametersample time blocks). For example, with reference to reference number 425of FIG. 4B, Constant1, Constant2, Lookup1, and SumB have been identifiedas a group of connected blocks to which the parameter sample time hasbeen assigned.

As further shown in FIG. 5A, process 500 may include generating anexecution list that includes the parameter sample time block (block525). For example, client device 210 (e.g., TCE 220) may generate anexecution list that includes the parameter sample time block, as shownby reference number 430. In some implementations, client device 210 maygenerate the execution list when client device 210 compiles the model.Additionally, or alternatively, client device 210 may generate theexecution list after client device 210 identifies the parameter sampletime block.

An execution list may include a list, a table etc. of blocks included inthe model that describes an order in which the blocks are to execute. Insome implementations, client device 210 may generate one or moreexecution lists, associated with the model, based on the sample times towhich the blocks of the model are assigned. For example, client device210 may generate a first execution list that includes the parametersample time block (e.g., or a group of parameter sample time blocks),and may create a second execution list that includes a group of blocksto which one or more other sample times are assigned (e.g., a discretesample time, a continuous sample time, etc.).

With regard to the execution list that includes the parameter sampletime block, in some implementations, client device 210 may generate theexecution list such that the execution list includes multiple parametersample time blocks. For example, client device 210 may generate anexecution list that includes all parameter sample time blocks includedin the model (e.g., a single execution list that includes all parametersample time blocks, regardless of grouping). Additionally, oralternatively, client device 210 may generate multiple execution lists,where each execution list includes a different parameter sample timeblock and/or different group of parameter sample time blocks. Forexample, client device 210 may identify a first group of connectedparameter sample time blocks, and a second group of parameter sampletime blocks. In this example, client device 210 may generate a firstexecution list that includes the first group of connected parametersample time blocks, and may generate a second execution list thatincludes the second group of connected parameter sample time blocks.

As further shown in FIG. 5A, process 500 may include causing the modelto be executed based on the execution list that includes the parametersample time block (block 530). For example, client device 210 (e.g., TCE220) may cause the model to be executed based on the execution list thatincludes the parameter sample time block, as shown by reference numbers435 and 440. In some implementations, client device 210 may cause themodel to be executed after client device 210 compiles the model.Additionally, or alternatively, client device 210 may cause the model tobe executed after client device 210 generates the execution list thatincludes the parameter sample time block.

In some implementations, client device 210 may cause the parametersample time block to be executed first when causing the model to beexecuted. For example, client device 210 may generate an execution listthat includes a group of parameter sample time blocks. In this example,client device 210 may cause the parameter sample time blocks, includedin the execution list, to be executed first during an initializationphase of the model execution and before other blocks included in otherexecution lists are executed. In this example, client device 210 mayexecute the group of parameter sample time blocks one time beforeproceeding with (e.g., repeatedly) executing the other blocks. In otherwords, client device 210 may cause parameter sample time blocks,included in the model, to be executed once before other blocks includedin the model are executed.

As further shown in FIG. 5A, process 500 may include detecting whether aparameter change event, associated with the model, occurs during theexecution of the model (block 535). For example, client device 210(e.g., TCE 220) may detect whether a parameter change event, associatedwith the model, occurs during the execution of the model. For example,in example implementation 400 described above, TCE 220 may detect theoccurrence of a parameter change event, associated with Model X, duringthe execution of Model X. In some implementations, client device 210 maydetect whether the parameter change event occurs while client device 210is causing the model to be executed. Additionally, or alternatively,client device 210 may detect whether the parameter change event occursafter client device 210 causes the parameter sample time block to beexecuted.

A parameter change event, associated with the model, may include anun-modeled event (e.g., an externally created event) that, whendetected, may cause a block (e.g., a parameter sample time block) to bere-executed. For example, the parameter change event may include anevent associated with a programmatic instruction, a programmatic event,and/or or user initiated input received by TCE 220 that causes TCE 220to modify, alter, update, etc. a parameter of one or more blocks inresponse to the event. As another example, the parameter change eventmay include a user interaction (e.g., opening a dialog box and modifyinga parameter of a block, interacting with an HMI associated with themodel, etc.) that causes a parameter of one or more blocks to bemodified. In these examples, client device 210 may detect that aparameter change event has occurred based on detecting that theparameter of the one or more blocks has been modified. In someimplementations, the externally created event may include an event otherthan a parameter change event, such as another type of event that may bedetected by client device 210 (e.g., an event based on a userinteraction, an event that occurs without any input from the user,etc.). In some implementations, client device 210 may pause and/orsuspend execution of the model based on detecting the parameter changeevent. Additionally, or alternatively, the user may pause and/or suspendthe execution of the model before client device 210 detects theparameter change event. Alternatively, the execution of the model maynot be paused upon detection of the parameter change event (e.g., theexecution of the model may continue without pausing the model).

In some implementations, client device 210 may detect the parameterchange event based on a user interaction. For example, client device 210may cause the model execution to begin, and client device 210 may pausethe execution of the model based on input from the user (e.g., aselection of a particular menu item, a click of a button, etc.). Theuser may then modify (e.g., via a dialog box associated with a block) aparameter associated with a block. Client device 210 may detect theparameter change event based on the user modifying the parameter of theblock. Additionally, or alternatively, client device 210 may detect theparameter change event based on a programmatic instruction, aprogrammatic event, user initiated input, etc. that causes TCE 220 tomodify the parameter of the block. In some implementations, theparameter change event may be associated with a parameter sample timeblock. Additionally, or alternatively, the parameter change event may beassociated with another block. For example, the user may modify aparameter of a first block (to which the parameter sample time isassigned), and may also modify a parameter of a second block (to whichanother type of sample time is assigned). In this example, TCE 220 maybe configured such that TCE 220 does not detect the parameter changeevent until the parameter of the second block is modified.

In some implementations, client device 210 may detect multiple parameterchange events during model execution. For example, client device 210 mayexecute the parameter sample time block, may proceed with executingother blocks of the model, and may detect a first parameter changeevent. Client device 210 may re-execute the parameter sample time blockbased on detecting the first parameter change event, and may continueexecuting the model, as described below. In this example, client device210 may detect a second parameter change event during the same executionof the model, may re-execute the parameter sample time block, and maycontinue executing the model until the model execution is complete(e.g., without detecting the occurrence of a third parameter changeevent). In this way, client device 210 may cause the parameter sampletime block to be executed only when necessary (e.g., based on upondetecting a parameter change event), while still allowing the parametersample time block to be responsive to parameter change events.

In some implementations, client device 210 may use the detection of theparameter change event in order to trigger further functionalityassociated with the model, such as logging data to a workspace, providestate information to the workspace, or the like. For example, the modelmay include a particular block that is configured to execute only upondetection of a parameter change event by client device 210. In thisexample, if client device 210 detects a parameter change event duringexecution of the model, then client device 210 may cause the particularblock to be executed in order to execute a function associated with theparticular block. For example, the block may compute its output values,may update its state values, may initiate a function call, or the like.

As further shown in FIG. 5A, if a parameter change event is not detectedduring the execution of the model (block 535—NO), then process 500 mayinclude providing a result of executing the model (block 540). Forexample, client device 210 (e.g., TCE 220) may not detect a parameterchange event during the execution of the model, and client device 210may provide a result of executing the model. An example of output isshown in relation to FIG. 4I. As another example, client device 210 maydetect a first parameter change event and may re-execute the parametersample time block (as described below). In this example, client device210 may not detect a second parameter change event during the execution,and client device 210 may provide a result of executing the model (e.g.,when the model execution is complete). The result may include, forexample, information determined during compilation of the model.Additionally, or alternatively, the result may include informationassociated with execution of the set of blocks included in the model,such as information relating to states of a computation, iterations ofthe model, etc. Additionally, or alternatively, the result may includeinformation associated with re-execution of the parameter sample timeblocks (e.g., information identifying parameter sample time blocks thatwere re-executed, information identifying one or more parameter sampletime blocks that caused one or more other blocks to be re-executed,information identifying a time during execution at which the parametersample time blocks were re-executed, etc.).

As further shown in FIG. 5A, if a parameter change event is detectedduring the execution of the model (block 535—YES), then, as shown inFIG. 5B, process 500 may include determining information associated withmodifying a parameter of one or more blocks of the set of blocksincluded in the model (block 545). For example, if client device 210(e.g., TCE 220) detects a parameter change event, then client device 210may determine information associated with modifying a parameter of oneor more blocks of the set of blocks included in the model (hereinreferred to as modification information).

In some implementations, client device 210 may determine themodification information based on user input. For example, the user mayprovide, via a dialog box associated with a block included in the model,input associated with modifying a parameter of the block, and clientdevice 210 may determine the modification information based on the userinput. For example, as shown in FIG. 4E, the user may provide inputassociated with modifying the constant value parameter of Constant2. Inthis example, TCE 220 may determine the modification information basedon the user input associated with modifying Constant 2.

As an additional example, the user may interact with an HMI, associatedwith TCE 220, and client device 210 may determine the modificationinformation based on information associated with the user interactionwith the HMI. For example, an HMI may include a virtual representation(e.g., a graphical depiction) of a physical mechanism (e.g., a dial, agauge, a slider, a lever, a button, etc.). The HMI may be configuredsuch that the user may interact with the HMI (e.g., via a click anddrag, etc.) in order to manipulate the HMI (e.g., to rotate a dial, tomove a lever, to depress a button, etc.). Here, manipulation of the HMImay cause one or more parameters of a parameter sample time block (e.g.,corresponding to the HMI) to be modified, and client device 210 maydetermine the modification information based on the manipulation of theHMI.

As another example, the user may interact with a logical workspace, viawhich a parameter is defined, in order to modify the parameter (e.g.,when the parameter is called in a parameter sample time block using asymbol that represents the parameter in the logical workspace), andclient device 210 may determine the modification information based oninformation provided by the user via the logical workspace.

In some implementations, the modification information may be associatedwith a parameter sample time block. Additionally, or alternatively, themodification information may be associated with multiple blocks (e.g.,when the user modifies one or more parameters associated with multipleblocks included in the model).

In some implementations, TCE 220 may perform a validation associatedwith the modification information (e.g., by determining whether themodified parameter lies within an allowable range, etc), perform aconversion associated with the modification information (e.g., byconverting a value from a first data type to a second data type, etc.),perform a confirmation associated with modification information (e.g.,by prompting the user to confirm the parameter change, etc.), and/orperform another type of task before accepting the modified parameter.

In some implementations, TCE 220 may store the modification informationto allow a parameter sample time block to be re-executed at a latertime. For example, if the user modifies a parameter of a parametersample time block included in a subsystem that is not enabled, then TCE220 may store the modification information to allow the parameter sampletime block to be re-executed at a later time, such as when the subsystemis enabled (e.g., after model execution resumes, at a later time duringexecution, etc.). Additionally, or alternatively, if TCE 220 isconfigured to ignore that the subsystem is not enabled, then TCE 220 mayexecute the parameter sample time block upon detecting the parameterchange event (e.g., TCE 22 may execute the parameter sample time blockimmediately).

In some implementations, TCE 220 may also determine protectioninformation associated with the model. Protection information mayinclude information indicating whether TCE 220 is to protect tasks,associated with executing the model, from being preempted as a result ofa parameter change event. For example, the user may pause the executionof the model at a time when TCE 220 is performing a task (e.g., writingto a memory location associated with a block) that may be affected bythe parameter change event. In this example, the protection informationmay be used to determine whether the task will be preempted by theparameter change event or whether TCE 220 will protect the task andallow the task to be completed without being affected by the parameterchange event. This protection may be similarly effected without pausingthe model by the user (e.g., when the parameter change event is detectedwhile the model is being executed). In some implementations, TCE 220 maydetermine the protection information based on user input (e.g., a globalsetting indicating whether TCE 220 is to protect tasks associated withthe model). Additionally, or alternatively, TCE 220 may determine theprotection information without user input (e.g., TCE 220 mayautomatically determine the protection information).

In some implementations, client device 210 may implement a parameterprotection technique based on receiving the modification information.For example, assume that a parameter (e.g., a numerical value) of aparameter sample time block is modified during model execution (e.g.,without pausing the execution of the model). Here, if the parameter ismodified as the numerical value is being read from memory, then acompromised numerical value may be obtained during execution of themodel. In some implementations, client device 210 may prevent acompromised value from being obtained by implementing a parameterprotection technique associated with modifying the parameter, such as byusing callback in a simulation loop in order to modify the storedparameter value, by buffering the parameter modification and updating ata later time, or the like.

In some implementations, the parameter protection technique may beassociated with executing the model on a first processor core andexecuting computations associated with modifying the parameter on asecond processor core. For example, execution threads associated withthe first processor core and the second processor core may communicatevia shared memory. Here, it may be desirable to ensure that, when avalue is read from the shared memory, the value is not beingconcurrently overwritten and/or modified. In such a case, computationsassociated with modifying the parameter (e.g., associated with theparameter change event) may be performed, but modified values may not bewritten to the shared memory. Rather, client device 210 may store thevalues in a separate memory location, and at a particular time (e.g.,upon completion of a current major time step) the model execution mayperform a method that determines whether modified values exist and, ifso, the shared memory may be updated with the modified values (e.g.,from the separate memory location) before continuing execution for thenext major time step.

In some implementations, client device 210 may not immediately effectthe parameter modification described by the modification information.For example, assume that a user modifies a parameter of a firstparameter sample time block, but also wishes to modify a parameter ofone or more other parameter sample time blocks (e.g., during executionof the model) before the parameter modification is effected. In thisexample, the user may indicate (e.g., via selection of a menu item,selection of a button, etc.) that client device 210 is not to effect theparameter modification to the first parameter sample time block (e.g.,in order to allow the user may make additional parameter modifications).In this example, client device 210 may provide an indication to the user(e.g., by changing a color of the block, graying out the block,displaying an asterisk near the block, etc.) that the first parametersample time block includes a parameter that has been modified withrespect to the parameter being used to execute the model.

At a later time (e.g., after the users finishes modifying one or moreother parameters), the user may provide (e.g., via an affordanceassociated with affecting the parameter modification) an indication toapply any parameter modifications made by the user, at which pointclient device 210 may effect the parameter modification to the firstparameter sample time block (e.g., and any other modifications made bythe user), and restore the visual appearance of the first parametersample time block. In some implementations, the indication to effect theparameter modification may be provided by the user. Additionally, oralternatively, the indication to effect the parameter modification maybe described by the model (e.g., by creating a block describing acondition that, when satisfied, triggers the parameter modification tobe affected).

As further shown in FIG. 5B, process 500 may include receiving anindication to resume executing of the model (block 550). For example,client device 210 (e.g., TCE 220) may receive an indication to resumeexecution of the model. In some implementations, client device 210 mayreceive the indication to resume the execution of the model after clientdevice 210 determines the modification information.

In some implementations, client device 210 may receive a command, fromthe user, to resume the execution of the model including the set ofblocks. In some implementations, client device 210 may receive thecommand based on detecting a selection of a particular menu item, entryof a particular textual or audible input from the user, and/or entry ofsome other predetermined input that identifies the desire to resume theexecution of the model. For example, as shown by reference number 465 ofFIG. 4E, after detecting the parameter change event associated withConstant2, TCE 220 may receive user input (e.g., via a Resume menu item)that the execution of Model X is to resume.

As further shown in FIG. 5B, process 500 may include determining theexecution list that includes the parameter sample time block (block555). For example, client device 210 (e.g., TCE 220) may determine theexecution list that includes the parameter sample time block. In someimplementations, client device 210 may determine the execution list thatincludes the parameter sample time block after client device 210receives the indication to resume the execution of the model.Additionally, or alternatively, client device 210 may determine theexecution list after client device 210 determines the modificationinformation (e.g., when the execution of the model is not paused basedon detecting the parameter change event).

In some implementations, client device 210 may determine the executionlist based on information stored by client device 210. For example,client device 210 may generate the execution list that includes theparameter sample time block, as discussed above, and may store theexecution list in a memory location of client device 210. In thisexample, client device 210 may determine the execution list based on thestored information.

In some implementations, client device 210 may determine the executionlist that includes the parameter sample time block regardless of whetherthe modification information is associated with the parameter sampletime block. For example, assume that a model contains a group ofparameter sample time blocks, included in a first execution list, and agroup of blocks assigned discrete sample times and included in a secondexecution list. Further, assume that client device 210 detects, duringexecution of the model, a parameter change event based on the usermodifying a parameter of a block included in the group of discretesample time blocks, and the user indicates that the model execution isto resume. In this example, client device 210 may determine theexecution list that includes the group of parameter sample time blockseven though none of the group of parameter sample time blocks weremodified by the user. In other words, client device 210 may cause theparameter sample time blocks to be re-executed when any parameter,associated with any block in the model, is modified. For example, asshown in FIG. 4F, TCE 220 may cause each parameter sample time block(e.g., Constant1, Constant2, Lookup1, and SumB) to be re-executed sincea parameter of a block included in Model X is modified. As anotherexample, with respect to FIG. 4, TCE 220 may cause each parameter sampletime block to be re-executed when a parameter of a block that is not aparameter sample time block is changed (e.g., TCE 220 may re-execute theparameter sample time blocks when a parameter of the Sine1 block (e.g.,an amplitude of the sine wave) is modified.

Additionally, or alternatively, client device 210 may determine theexecution list that includes the parameter sample time block only when aparameter sample time block, included in the execution list thatincludes the parameter sample time block, is modified. For example, TCE220 may determine the execution list that includes the parameter sampletime blocks, and may identify a subset of parameter sample time blocks,included in the execution list, that is to be executed in response tothe parameter change event. In this example, TCE 220 may apply adaptivere-execution by identifying a subset of blocks of the group of parametersample time blocks that are affected by the parameter change event, andcausing the subset of blocks to be executed accordingly (e.g., ratherthan causing all of the parameter sample time blocks in the group ofparameter sample time blocks to be re-executed). This example isillustrated in FIG. 4G. As shown in FIG. 4G, TCE 220 may apply adaptivere-execution by causing only those parameter sample time blocks affectedby the parameter change event (e.g., Constant2, Lookup1, and SumB) to bere-executed (e.g., since Constant1 was not affected by the parameterchange event).

As another example, TCE 220 may determine the execution list thatincludes the parameter sample time blocks, and may identify a parametersample time block, included in the execution list, that is not to beexecuted in response to the parameter change event. In this example, TCE220 may apply adaptive re-execution by identifying that the parametersample time block, of the group of parameter sample time blocks,references a parameter that is defined as being non-tunable (e.g., aparameter that cannot be modified) after the execution of the model hasstarted (e.g., after time t=0). Here, the parameter sample time blockmay reference a parameter that is defined independently of the blockthat references the parameter. For example, the user may define, via acommand prompt associated with TCE 220, a parameter (e.g., P) using aparticular command (e.g., P=parameter), may define a value of theparameter (e.g., P.value=3.4), and may define a tunability property ofthe parameter (e.g., P.tunability=@ t=0 only) indicating that theparameter may not be tuned after the execution of the model has begun.The user may then indicate that the parameter sample time block is toreference the defined parameter during model execution (e.g., by callingP within a parameter dialog box associated with the parameter sampletime block). In this example, TCE 220 may determine the execution listthat includes the parameter sample time block, may determine (e.g.,based on the tunability property of P), that the parameter sample timeblock is not to be re-executed, and may cause other parameter sampletime blocks, included in execution list, to be re-executed. In someimplementations, as described in the above example, the tunabilityproperty may identify a time at which the parameter may be tuned or maynot be tuned. Additionally, or alternatively, the tunability propertymay identify a time window during which the parameter may be tuned ormay not be tuned (e.g., a tunability property indicating that theparameter may not be tuned during a first five seconds of modelexecution, a tunability property indicating that the parameter may betuned between ten and fifteen seconds after the execution begins), amodification threshold associated with the parameter (e.g., a tunabilityproperty indicating that the parameter may be tuned if a value of theparameter is modified by less than a maximum amount, a tunabilityproperty indicating that the parameter may be tuned if a value of theparameter is modified by greater than a minimum amount, etc.).

As further shown in FIG. 5B, process 500 may include causing theparameter sample time block to be re-executed based on determining theexecution list (block 560). For example, client device 210 (e.g., TCE220) may cause the parameter sample time block to be re-executed basedon determining the execution list that includes the parameter sampletime block. In some implementations, client device 210 may cause theparameter sample time block to be re-executed after client device 210determines the execution list. Additionally, or alternatively, clientdevice 210 may cause the parameter sample time block to be re-executedafter client device 210 receives the indication to resume the executionof the model.

In some implementations, client device 210 may cause the parametersample time block to be re-executed first when resuming the execution ofthe model. For example, client device 210 may cause the parameter sampletime block, included in the execution list, to be executed first whenthe model execution resumes (e.g., before other blocks included in otherexecution lists are executed). In this example, client device 210 maycause the parameter sample time block to be re-executed one time beforeproceeding with (e.g., repeatedly) executing the other blocks. In otherwords, client device 210 may cause parameter sample time block, includedin the model, to be executed once when the execution of the modelresumes. For example, as shown in FIG. 4F, TCE 220 may cause each of theparameter sample time blocks to be re-executed before proceeding withexecuting the other blocks of Model X. As another example, as shown inFIG. 4G, TCE 220 may cause a subset of the parameter sample time blocksto be re-executed before proceeding with executing the other blocks ofModel X.

As further shown in FIG. 5B, process 500 may include resuming theexecution of the model based on causing the parameter sample time blockto be re-executed (block 565). For example, client device 210 (e.g., TCE220) may resume the execution of the model based on causing theparameter sample time block to be re-executed. In some implementations,client device 210 may resume the execution of the model after clientdevice 210 causes the parameter sample time block to be re-executed. Forexample, as shown in FIG. 4H, TCE 220 may resume the execution of ModelX after TCE 220 causes the parameter sample time blocks to bere-executed.

Returning to FIG. 5B, in some implementations, client device 210 mayresume the execution of the model, and process 500 may return to block535. For example, client device 210 may resume the execution of themodel, and client device 210 may wait to detect another parameter changeevent during the execution of the model. If client device 210 detectsanother parameter change event, then blocks 545 through block 565 may berepeated. This process may repeat until client device 210 does notdetect a parameter change event and the execution of the model iscomplete. Client device 210 may then provide a result of executing themodel, as described above with regard to block 540. In someimplementations, client device 210 may provide the result of executingthe model (e.g., continuously) during execution of the model.

Although FIGS. 5A and 5B shows example blocks of process 500, in someimplementations, process 500 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIGS. 5A and 5B. Additionally, or alternatively, two or moreof the blocks of process 500 may be performed in parallel.

Implementations described herein may allow for detecting an un-modeledevent during an execution of a model, causing one or more blocks,included in the model, to be re-executed in response to the un-modeledevent, and continuing the execution of the model after causing the oneor more blocks to be re-executed.

The foregoing disclosure provides illustration and description, but isnot intended to be exhaustive or to limit the implementations to theprecise form disclosed. Modifications and variations are possible inlight of the above disclosure or may be acquired from practice of theimplementations. For example, while implementations and/or examplesdescribed herein are described in the context of a parameter changeevent occurring while an execution of the model is paused, in otherimplementations and/or other examples, the parameter change event (e.g.,and subsequent re-execution of parameter sample time blocks) may occurduring model execution (i.e., without pausing the execution of themodel).

As used herein, the term component is intended to be broadly construedas hardware, firmware, and/or a combination of hardware and software.

Program code (sometimes referred to herein as code) is to be broadlyinterpreted to include text-based code that may not require furtherprocessing to execute (e.g., C++ code, Hardware Description Language(HDL) code, very-high-speed integrated circuits (VHSIC) HDL (VHDL) code,Verilog code, Java code, another type of hardware and/or software basedcode that may be compiled and/or synthesized, etc.), binary code thatmay be executed (e.g., executable files that may be directly executed byan operating system, bitstream files that may be used to configure anFPGA, Java byte code, object files combined together with linkerdirectives, source code, makefiles, etc.), text files that may beexecuted in conjunction with other executables (e.g., Python text files,Octave files, a collection of dynamic-link library (DLL) files withtext-based combining, configuration information that connectspre-compiled modules, an extensible markup language (XML) filedescribing module linkage, etc.), source code (e.g., readable by ahuman), machine code (e.g., readable by a machine), or the like. In someimplementations, program code may include different combinations of theabove-identified classes of code (e.g., text-based code, binary code,text files, source code, machine code, etc.). Additionally, oralternatively, program code may include code generated using adynamically-typed programming language (e.g., the M language, a MATLAB®language, a MATLAB-compatible language, a MATLAB-like language, etc.)that may be used to express problems and/or solutions using mathematicalnotations. Additionally, or alternatively, program code may be of anytype, such as a function, a script, an object, etc.

Certain user interfaces have been described herein and/or shown in thefigures. A user interface may include a graphical user interface, anon-graphical user interface, a text-based user interface, etc. A userinterface may provide information for display. In some implementations,a user may interact with the information, such as by providing input viaan input component of a device that provides the user interface fordisplay. In some implementations, a user interface may be configurableby a device and/or a user (e.g., a user may change the size of the userinterface, information provided via the user interface, a position ofinformation provided via the user interface, etc.). Additionally, oralternatively, a user interface may be pre-configured to a standardconfiguration, a specific configuration based on a type of device onwhich the user interface is displayed, and/or a set of configurationsbased on capabilities and/or specifications associated with a device onwhich the user interface is displayed.

It will be apparent that systems and/or methods, described herein, maybe implemented in different forms of hardware, firmware, or acombination of hardware and software. The actual specialized controlhardware or software code used to implement these systems and/or methodsis not limiting of the implementations. Thus, the operation and behaviorof the systems and/or methods were described herein without reference tospecific software code—it being understood that software and hardwarecan be designed to implement the systems and/or methods based on thedescription herein.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of possible implementations. In fact,many of these features may be combined in ways not specifically recitedin the claims and/or disclosed in the specification. Although eachdependent claim listed below may directly depend on only one claim, thedisclosure of possible implementations includes each dependent claim incombination with every other claim in the claim set.

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems, and may be used interchangeably with “one or more.” Furthermore,as used herein, the term “set” is intended to include one or more items,and may be used interchangeably with “one or more.” Where only one itemis intended, the term “one” or similar language is used. Also, as usedherein, the terms “has,” “have,” “having,” or the like are intended tobe open-ended terms. Further, the phrase “based on” is intended to mean“based, at least in part, on” unless explicitly stated otherwise.

What is claimed is:
 1. A device, comprising: one or more processors to:receive a model including a group of blocks; receive a command toexecute the model; assign, based on receiving the command, a parametersample time to a subset of blocks of the group of blocks, the parametersample time permitting a block, of the subset of blocks, to be executedbased on a parameter change event detected during the execution of themodel; cause the model to be executed after assigning the parametersample time to the subset of blocks; detect a parameter change event,associated with the model, prior to the execution of the model beingcompleted, the parameter change event including an event that isexternal to the execution of the model; cause at least one block, of thesubset of blocks, to be executed based on the detecting the parameterchange event.
 2. The device of claim 1, where the parameter sample timeindicates that each block, of the subset of blocks, is to be executed ata start of the execution of the model; and where the one or moreprocessors, when causing the model to be executed after assigning theparameter sample time to the subset of blocks, are further to: cause thesubset of blocks to be executed at a start of the execution of themodel.
 3. The device of claim 1, where the one or more processors, afterdetecting the parameter change event, are further to: cause theexecution of the model to pause, the execution of the model being pausedwhile the at least one block, of the subset of blocks, is executed basedon detecting the parameter change event; and cause the execution of themodel to resume after the at least one block is executed based ondetecting the parameter change event.
 4. The device of claim 1, wherethe one or more processors, when causing the at least one block, of thesubset of blocks, to be executed, are to: cause the at least on block tobe executed without pausing the execution of the model.
 5. The device ofclaim 1, where the one or more processors are further to: identify oneor more blocks, of the subset of blocks, that are affected by theparameter change event; and where the one or more processors, whencausing the at least one block, of the subset of blocks, to be executedbased on detecting the parameter change event, are further to: cause theone or more blocks that are affected by the parameter change event to beexecuted, at least one other block, of the subset of blocks, not beingexecuted based on the detecting the parameter change event.
 6. Thedevice of claim 1, where the one or more processors, when causing the atleast one block, of the subset of blocks, to be executed, are to: causethe at least one block to be executed by a target device associated withthe model.
 7. The device of claim 1, where the one or more processorsare further to: identify a user interaction associated with the model,the user interaction occurring during the execution of the model, andthe user interaction being associated with a dialog box for modifying aparameter of a block included in the group of blocks; and where the oneor more processors, when detecting the parameter change event, arefurther to: detect the parameter change event based on the userinteraction associated with the model.
 8. A computer-readable mediumstoring instructions, the instructions comprising: one or moreinstructions that, when executed by one or more processors, cause theone or more processors to: receive a command to execute a modelincluding a group of blocks; compile the model based on receiving thecommand, a parameter sample time being assigned to a subset of blocks,of the group of blocks, during the compiling, the parameter sample timeallowing a block, of the subset of blocks, to be executed based on anexternally created event detected during the execution of the model;cause the model to be executed based on compiling the model; detect theexternally created event before the execution of the model is completed;cause at least one block, of the subset of blocks, to be executed basedon detecting the externally created event; and provide a result ofexecuting the model.
 9. The computer-readable medium of claim 8, wherethe one or more instructions, when executed by the one or moreprocessors, further cause the one or more processors to: determine a setof sample time propagation rules associated with the parameter sampletime; and where the one or more instructions, that cause the one or moreprocessors to assign the parameter sample time to the subset of blocks,further cause the one or more processors to: assign the parameter sampletime to the subset of blocks based on the set of sample time propagationrules.
 10. The computer-readable medium of claim 8, where the one ormore instructions, that cause the one or more processors to cause atleast one block, of the subset of blocks, to be executed based ondetecting the externally created event, cause the one or more processorsto: cause the at least one block, of the subset of blocks, to beexecuted without pausing the execution of the model.
 11. Thecomputer-readable medium of claim 8, where the one or more instructions,when executed by the one or more processors, further cause the one ormore processors to: generate program code associated with the model, theprogram code being generated such that a portion of the program code isgenerated into a start method of the model, the portion of the programcode including program code corresponding to at least one block, of thesubset of blocks, to which the parameter sample time is assigned. 12.The computer-readable medium of claim 8, where the one or moreinstructions, when executed by the one or more processors, further causethe one or more processors to: generate program code associated with themodel, the program code being generated such that a portion of theprogram code is generated into an output method of another block of thegroup of blocks, the portion of the program code including program codethat corresponds to at least one block, of the subset of blocks, towhich the parameter sample time is assigned, and the other block, of thegroup of blocks, being a block that lies downstream from the at leastone block, of the subset of blocks, to which the parameter sample timeis assigned.
 13. The computer-readable medium of claim 12, where the oneor more instructions, that cause the one or more processors to generatethe program code associated with the model, further cause the one ormore processors to: compute an output of a block included in the subsetof blocks, the block including a parameter that may not be modifiedduring the execution of the model; store the output of the block,generate the program code such that stored output is referenced in theprogram code, the stored output being referenced allowing the output ofthe block to be statically determined during execution of the programcode.
 14. The computer-readable medium of claim 8, where the one or moreinstructions, when executed by the one or more processors, further causethe one or more processors to: identify a user interaction associatedwith the model, the user interaction occurring during the execution ofthe model, and the user interaction being associated with a humanmachine interface (HMI) for modifying a parameter of a block included inthe subset of blocks; and where the one or more instructions, that causethe one or more processors to detect the externally created event,further cause the one or more processors to: detect the externallycreated event based on the user interaction associated with the model.15. The computer-readable medium of claim 8, where the one or moreinstructions, that cause the one or more processors to cause the atleast one block, of the subset of blocks, to be executed, cause at leastone block to be executed by a host device associated with the model. 16.A method, comprising: receiving a model including multiple blocks, thereceiving the model being performed by a device; receiving a command toexecute the model, the receiving the command being performed by thedevice; and compiling the model based on receiving the command, thecompiling the model including: assigning a sample time to a subset ofblocks of the multiple blocks, the sample time permitting a block, ofthe subset of blocks, to be executed based on an un-modeled eventidentified during an execution of the model, and the compiling the modelbeing performed by the device.
 17. The method of claim 16, furthercomprising: causing the model to be executed based on compiling themodel; identifying the un-modeled event, associated with the model,prior to the execution of the model completing; and causing one or moreblocks, of the subset of blocks, to be executed based on identifying theun-modeled event.
 18. The method of claim 17, where causing the one ormore blocks, of the subset of blocks, to be executed based onidentifying the un-modeled further comprises: receiving user inputindicating that the one or more blocks are to be executed; and causingthe one or more blocks to be executed based on receiving the user input.19. The method of claim 17 where causing the one or more blocks, of thesubset of blocks, to be executed further comprises: causing each block,of the subset of blocks, to be executed after identifying the un-modeledevent.
 20. The method of claim 17, further comprising: identifying auser interaction associated with the model, the user interactionoccurring during the execution of the model, and the user interactionbeing associated with a block, of the multiple blocks, that is notincluded in the subset of blocks; and where identifying the un-modeledevent further comprises: identifying the un-modeled event based on theuser interaction associated with the model.
 21. The method of claim 17,further comprising: obtaining static scheduling information, associatedwith the one or more blocks, the static scheduling information beingdetermined during compilation of the model; and where causing the one ormore blocks, of the subset of blocks, to be executed based onidentifying the un-modeled event further comprises: causing the one ormore blocks to be executed in accordance with the static schedulinginformation.
 22. The method of claim 16, further comprising: generatingprogram code associated with the model, the generated program codeincluding a separate entry point for program code that corresponds to atleast one block, of the subset of blocks, to which the sample time isassigned.